-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added ship_traffic AIS example #130
Conversation
Very nice! This data generates some very pretty plots.
I'm currently working on different approaches to do this. Right now I have one prototype (that needs to be better encapsulated) but I am also working on a more efficient approach which will probably be needed for this large dataset. |
Together with @philippjfr, we identified the reason for the massive performance difference: you want to use |
Also writing the parquet file, it goes from 30 minutes -> 10 minutes, while reading goes from 10 minutes -> 10 seconds. |
Co-authored-by: Philipp Rudiger <[email protected]>
Co-authored-by: Philipp Rudiger <[email protected]>
I'm guessing the data is from this page and obtained using:
And 49.3GB in size. |
In 136c358 I added a (slow! non spatially indexed!) prototype of the |
@jbednar Now you can use holoviz/holoviews#4794 which is branched off master instead of holoviz/holoviews#4796 |
This notebook/dashboard shows USA AIS vessel (typically ship) tracking data collected from marinecadastre, colored by vessel type:
Apart from the actual data shown, which is interesting enough, the notebook also shows:
To do items:
['imo', 'call_sign', 'vessel_name', 'vessel_type','length', 'width']
for each'mmsi_id'
. This data shouldn't vary per ping, and can be stored separately from the ping data.